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

IAC-772 Fixed project IDs for resources #147

Merged
merged 7 commits into from
Jul 27, 2023
Merged

IAC-772 Fixed project IDs for resources #147

merged 7 commits into from
Jul 27, 2023

Conversation

iludart
Copy link
Contributor

@iludart iludart commented Jul 12, 2023

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

  • Lint and unit tests pass locally with my changes
  • I have added relevant error handling and logging messages to help troubleshooting
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)
  • I have updated CHANGELOG.md with a short summary of the changes introduced
  • I have tested against live environment, if applicable
  • I have added relevant usage information (As-built)
  • Any structure and/or content vRA-NG improvements are synchronized with vra-ng and ts-vra-ng archetypes
  • Every new or updated Installer property is documented in docs/archive/doc/markdown/use-bundle-installer.md
  • Dependencies in pom.xml are up-to-date
  • My changes have been rebased and squashed to the minimal number of relevant commits
  • My changes have a descriptive commit message with a short title, including a Fixed #XXX - or Closed #XXX - prefix to auto-close the issue

Testing

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

Signed-off-by: Petar Penev <[email protected]>

Signed-off-by: Petar Penev <[email protected]>
@iludart iludart requested a review from a team as a code owner July 12, 2023 08:29
@iludart iludart changed the title Fixed project IDs for resources IAC-772 Fixed project IDs for resources Jul 12, 2023
Signed-off-by: Petar Penev <[email protected]>

Signed-off-by: Petar Penev <[email protected]>
Copy link
Collaborator

@Michaelpalacce Michaelpalacce left a 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?

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

iludart commented Jul 24, 2023

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).

@Michaelpalacce
Copy link
Collaborator

@iludart makes sense to me :)

@Michaelpalacce Michaelpalacce merged commit b3e34fc into main Jul 27, 2023
11 checks passed
@VenelinBakalov VenelinBakalov deleted the IAC-772 branch November 1, 2024 10:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants