-
Notifications
You must be signed in to change notification settings - Fork 24
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
IAC-772 Fixed project IDs for resources #147
Conversation
Signed-off-by: Petar Penev <[email protected]> Signed-off-by: Petar Penev <[email protected]>
Signed-off-by: Petar Penev <[email protected]> Signed-off-by: Petar Penev <[email protected]>
…re-aria into IAC-772 Signed-off-by: Petar Penev <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Release.md also needs to be modified.
Shouldn't we also test the VraNgCustomResourceStore + VraNgResourceActionStore?
common/artifact-manager/src/main/java/com/vmware/pscoe/iac/artifact/utils/VraNgProjectUtil.java
Outdated
Show resolved
Hide resolved
...anager/src/main/java/com/vmware/pscoe/iac/artifact/store/vrang/VraNgCustomResourceStore.java
Outdated
Show resolved
Hide resolved
...anager/src/main/java/com/vmware/pscoe/iac/artifact/store/vrang/VraNgResourceActionStore.java
Outdated
Show resolved
Hide resolved
...artifact-manager/src/test/java/com/vmware/pscoe/iac/artifact/utils/VraNgProjectUtilTest.java
Outdated
Show resolved
Hide resolved
Signed-off-by: Petar Penev <[email protected]>
Well, VraNgCustomResourceStore and VraNgResourceActionStore don't actually hold any logic that is related to this. Currently there are tests that cover the innermost piece that handles project id for custom resources and resource actions so I don't think it is necessary to test if it is called or not (it is not conditional). |
Signed-off-by: Petar Penev <[email protected]>
Signed-off-by: Petar Penev <[email protected]>
Signed-off-by: Petar Penev <[email protected]>
@iludart makes sense to me :) |
Description
When pushing Resource Actions (RAs), the ones that are scoped to a single project now have their projectId modified to be the same as in the configuration.
Checklist
Fixed #XXX -
orClosed #XXX -
prefix to auto-close the issueTesting
Tested pushing Resource Actions to a vApp environment. Performed tests with resource actions scoped to a single project and they have their projectId modified. Also tested with global resource actions (without projectId) and those are not modified.
Related issues and PRs
https://jira.pscoe.vmware.com/browse/IAC-772