-
Notifications
You must be signed in to change notification settings - Fork 53
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
Creating m2 group with version_policy = "SNAPSHOT"
produces a group repo with version policy as Release
#148
Comments
thanks for your report. here is the important excerpt from api version 3.37:
I am sorry that this cannot be seen. We are in the process of splitting up the repository resource so that everything is easier to use. regards |
Issue at nexus jira is created. here: https://issues.sonatype.org/browse/NEXUS-30501 |
So...to be clear....the Nexus API forces you to select an option that cannot be changed at a later date. #genius 😄 Also...thanks! I'll try to work that from my end, as well. |
And just so everyone understands why, it appears that if I set the version_policy to release, then it only resolves releases. Thus a true snapshot group seems effectively impossible to produce with this provider at the present time. |
This issue has been automatically marked as |
Describe the bug
terraform plan
tells me the following as part of the attached TF files run (this is a subset)To Reproduce
op2-snapshot-group-m2
is of typeRelease
Expected behavior
op2-snapshot-group-m2
should have version policy ofSnapshot
The text was updated successfully, but these errors were encountered: