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

[PPANTT-106] feat: Introduced liquidbase changelog for data_creazione #2402

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

alessio-cialini
Copy link
Collaborator

@alessio-cialini alessio-cialini commented Sep 5, 2024

List of changes

  • Introducing data_creazione property to stazioni withing cfg database

Motivation and context

Type of changes

  • Add new resources
  • Update configuration to existing resources
  • Remove existing resources

Does this introduce a change to production resources with possible user impact?

  • Yes, users may be impacted applying this change
  • No

Does this introduce an unwanted change on infrastructure? Check terraform plan execution result

  • Yes
  • No

Other information


If PR is partially applied, why? (reserved to mantainers)

@alessio-cialini alessio-cialini added env: dev The status refers to DEV environment status: ready to apply labels Sep 5, 2024
@alessio-cialini alessio-cialini requested review from a team as code owners September 5, 2024 14:36
@alessio-cialini alessio-cialini changed the title [PPANTT-106] feat: Introduced liquidbase changelog for data_creazione… [PPANTT-106] feat: Introduced liquidbase changelog for data_creazione Sep 5, 2024
Copy link
Contributor

@jacopocarlini jacopocarlini left a comment

Choose a reason for hiding this comment

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

you need to create the 3.31.0 in all schema.
Create a empty 3.31.0 version in all directories inside the changelog folder.
here an example

@pasqualespica pasqualespica marked this pull request as draft December 2, 2024 15:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
env: dev The status refers to DEV environment status: ready to apply
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants