Skip to content
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 resource_deployment.go to switch from blueprint to day2 action… #495

Merged
merged 1 commit into from
Jun 7, 2023

Conversation

an2ane
Copy link
Contributor

@an2ane an2ane commented May 30, 2023

… schema as blueprint API is based on Assembler rights only

… schema as blueprint API is based on Assembler rights only

Signed-off-by: an2ane <[email protected]>
@an2ane
Copy link
Contributor Author

an2ane commented May 30, 2023

The previous change was working great, for people that had Assembler rights. However, our customers don't have this right.
The update action has basically all the information needed to update an unreleased version of a catalog item.

@frodenas frodenas merged commit a380dea into vmware:main Jun 7, 2023
@gthieleb
Copy link

gthieleb commented Sep 8, 2023

an2ane: Is this helping with this one? #496

@an2ane
Copy link
Contributor Author

an2ane commented Sep 12, 2023

an2ane: Is this helping with this one? #496

This was a fix I made for deployments based on a blueprint version no longer available (unrelease in Assembler). Before, when the version was not available, the provider exited in 404 error. Now, it checks the form based on the "Update" day-2 action.

I don't think this what you are looking for. If your account is not an Assembler Administrator/User, you won't be able to fetch the Blueprint template. With the Service Broker Administrator/User rights, you will only get the Catalog Item inputs.

@vmware vmware locked as resolved and limited conversation to collaborators Jun 29, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants