-
Notifications
You must be signed in to change notification settings - Fork 674
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
Update terraform to the latest API level for Project service #4813
Conversation
Signed-off-by: dvesperini <[email protected]>
Signed-off-by: dvesperini <[email protected]>
Signed-off-by: dvesperini <[email protected]>
Signed-off-by: dvesperini <[email protected]>
Signed-off-by: dvesperini <[email protected]>
Signed-off-by: dvesperini <[email protected]>
Signed-off-by: dvesperini <[email protected]>
Signed-off-by: dvesperini <[email protected]>
Signed-off-by: dvesperini <[email protected]>
Signed-off-by: dvesperini <[email protected]>
Signed-off-by: dvesperini <[email protected]>
Signed-off-by: dvesperini <[email protected]>
Merge master to test
@hkantare please do another review |
will review can you fix conflcits for above files |
conflicts fixed |
# Conflicts: # .secrets.baseline
@hkantare the code generator has been fixed, can you do another review? we went to staging today and plan to go to production on November 6th |
@riccardo-angelilli It will be breaking change for users who may use those old resources |
We have removed all the old code from the swagger.yaml and from the back end code, now it's almost impossible to restore the old code. No one has used the ProjectEventNotification resource until today, it was wrongly defined at first terraform code generation in May. |
Community Note
Relates OR Closes #0000
Output from acceptance testing: