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

Swift v1: add support for new object versioning #1498

Merged

Conversation

kayrus
Copy link
Collaborator

@kayrus kayrus commented Feb 28, 2023

Fixes #1489

@kayrus
Copy link
Collaborator Author

kayrus commented Feb 28, 2023

@ozerovandrei please review.

Copy link
Member

@nikParasyr nikParasyr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is still a breaking change right?
The stateUpgrader will "move" what was on versioning to versioning_legacy but the user will still have to update his resource definition.
Or did i misunderstood something?

Moreover for some reason the tests are being skipped:

2023-02-28T20:52:42.1952225Z === RUN   TestAccObjectStorageV1Container_versioning
2023-02-28T20:52:42.1953883Z 2023-02-28T20:52:42.195Z [DEBUG] sdk.helper_resource: Starting TestCase: test_name=TestAccObjectStorageV1Container_versioning
2023-02-28T20:52:42.1954805Z 2023-02-28T20:52:42.195Z [DEBUG] sdk.helper_resource: Calling TestCase PreCheck: test_name=TestAccObjectStorageV1Container_versioning
2023-02-28T20:52:42.1955825Z     provider_test.go:270: this is not supported below stable/ussuri, testing in 
2023-02-28T20:52:42.1956481Z --- SKIP: TestAccObjectStorageV1Container_versioning (0.00s)
2023-02-28T20:52:42.1958238Z PASS

Ill try to find some time to see why

@kayrus
Copy link
Collaborator Author

kayrus commented Mar 1, 2023

This is still a breaking change right? The stateUpgrader will "move" what was on versioning to versioning_legacy but the user will still have to update his resource definition.

correct. I think this is the most optimal solution.

Moreover for some reason the tests are being skipped:

hm... you're right... testAccSkipReleasesBelow(t, "stable/ussuri") doesn't work as intended.

Copy link
Member

@nikParasyr nikParasyr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok. tests seem to be running now and passing:

2023-03-01T07:25:46.8268716Z 2023-03-01T07:25:46.820Z [DEBUG] sdk.helper_resource: Called TestCase CheckDestroy: test_name=TestAccObjectStorageV1Container_versioning test_terraform_path=/tmp/plugintest-terraform3968591059/terraform test_working_directory=/tmp/plugintest195555014 test_step_number=1
2023-03-01T07:25:46.8269514Z 2023-03-01T07:25:46.820Z [DEBUG] sdk.helper_resource: Finished TestCase: test_name=TestAccObjectStorageV1Container_versioning
2023-03-01T07:25:46.8333324Z --- PASS: TestAccObjectStorageV1Container_versioning (3.15s)

I'll create an issue to have a look at why the testAccSkipReleasesBelow was not working as expected.

LGTM as long as we are ok with the breaking change (i do think as well thats it's the best way forward). Would like @ozerovandrei opinion as well

Copy link
Member

@ozerovandrei ozerovandrei left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@nikParasyr nikParasyr merged commit 2c5b898 into terraform-provider-openstack:main Mar 1, 2023
@kayrus kayrus deleted the container-versioning branch March 1, 2023 12:30
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.

Swift V1: Add support for objects versioning
3 participants