Skip to content
This repository has been archived by the owner on May 23, 2024. It is now read-only.

Tower 3.3 removed result_stdout field from project_update #122

Merged
merged 1 commit into from
Nov 16, 2018

Conversation

jameswnl
Copy link
Contributor

@jameswnl jameswnl commented Nov 9, 2018

@miq-bot miq-bot added the wip label Nov 9, 2018
@jameswnl jameswnl changed the title [WIP] Tower 3.3 removed result_stdout field from project_update Tower 3.3 removed result_stdout field from project_update Nov 9, 2018
@miq-bot miq-bot removed the wip label Nov 9, 2018
@jameswnl
Copy link
Contributor Author

jameswnl commented Nov 9, 2018

@miq-bot remove_label wip
@miq-bot add_labels bug, hammer/yes

@miq-bot
Copy link
Collaborator

miq-bot commented Nov 9, 2018

@jameswnl Cannot apply the following label because they are not recognized: hammer/yes

@miq-bot miq-bot added the bug label Nov 9, 2018
@jameswnl
Copy link
Contributor Author

jameswnl commented Nov 9, 2018

@miq-bot assign @gmcculloug

@miq-bot
Copy link
Collaborator

miq-bot commented Nov 9, 2018

Checked commit jameswnl@2ba210c with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0
2 files checked, 0 offenses detected
Everything looks fine. 🍪

def stdout(format = 'txt')
api.get("#{related['stdout']}?format=#{format}").body
end
alias result_stdout stdout
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this need to be a version dependent patch? Will this break older versions?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no. I checked and this is available since 3.1

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we still support versions older than 3.1?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure.
At least 3.0 reached End of Maintenance Support 2 (EOL) on 2/28/18 according to
https://access.redhat.com/support/policy/updates/ansible-tower

We started supporting Embedded Tower since 3.1. I am not sure about the external integration. Do you remember what version of Tower is the first integrated by MIQ?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this change is intended to fix master and hammer branches I think we should be ok here based on the Tower EOL for 3.0.

def stdout(format = 'txt')
api.get("#{related['stdout']}?format=#{format}").body
end
alias result_stdout stdout
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why add the alias?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the miq tower gem is depending on this alias

@jameswnl
Copy link
Contributor Author

@gmcculloug @bdunne anything else needed for this to be merged?

@gmcculloug
Copy link
Contributor

I'm good with it. @bdunne any issue merging?

@bdunne bdunne merged commit 09fd8d3 into ansible:master Nov 16, 2018
@bdunne bdunne assigned bdunne and unassigned gmcculloug Nov 16, 2018
@jameswnl
Copy link
Contributor Author

@bdunne can you create a tag to contain this fix?

@bdunne
Copy link
Contributor

bdunne commented Nov 19, 2018

@jameswnl v0.19.0 has been released

@jameswnl jameswnl deleted the stdout branch November 26, 2018 20:49
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants