-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updating a Job Template Resource does not take the changes #115
Comments
Fixing that may be as simple as adding:
Here: That way when you modify a JobTemplate resource, it will kick off the reconciliation lop again, which will run the awx.awx.job_template task to update the JobTemplate. We just have to make sure that there aren't other knock-on effects to this change that are unwanted. |
/assign |
I think that if we do this, we should make it possible to configure whether the state described in the CR for resources should be maintained or just created once. This could be an environment variable set on the operator deployment (for all resources) or it could be configurable on each resource. Maybe we could call it This would allow users to either: @cooktheryan Another thing is that we may want to make it possible to optionally configure a custom reconciliation interval, this way an AWX admin could enforce that changes made by users in the AWX UI were overwritten regularly if that is the desired behavior. That is how many configuration as code Jenkins instances are set up. |
@rooftopcellist so all of the items except jobtemplate and workflowtemplate I have working. The problem seems to exist that with the field @rlopez133 specified the underlying ansible playbook does not attempt to remediate those values. For example
Changing the value of the playbook causes the underlying playbook to make the change
So I'm wondering if this is something that would need to happen in the job_template official playbook rather than this operator. Unless we wanted to remove objects if they already exist. I can modify the job_template_playbook as well as the job_template_project and the underlying playbook will make the change. PR #129 |
Currently if I created a Job Template as such on the first attempt this would create as expected.
If I wanted to make a change and say remove the job_template_credentials from the Job Template if I went ahead removed this piece and gave another unique metadata.name , when you apply, you don't see the changes to the Job Template where the template credential is removed. It's exactly the same as the initial creation.
The text was updated successfully, but these errors were encountered: