Flyway Placeholders are not saved in the project

Answers

• Options

  Peter_Laws Redgate › Posts: 220 Silver 2

  August 31, 2023 8:38AM

  Hi javaDuke,
  
  It could be either; how are you defining them and in what context please?

  Kind regards

  Peter Laws | Redgate Software

  Have you visited our Help Center?

  0 · Share on Twitter
• Options

  javaDuke Posts: 12 Bronze 1

  August 31, 2023 2:15PM

  I'm defining for a migrate operation in the "flyway parameters" section
  
  

  0 · Share on Twitter
• Options

  javaDuke Posts: 12 Bronze 1

  August 31, 2023 3:26PM

  Thank you for the insight! That can work 
  In a multi-env/team environment where one delivers the script and the other team applies to a different environments like (DEV, UAT, PROD, etc) is it possible to defile some sort of "profiles" that contain values for the placeholders specific to the target environment?

  1 · Share on Twitter
• Options

  javaDuke Posts: 12 Bronze 1

  September 1, 2023 2:27PM

  Peter_Laws said:

  As the interface says, these parameters are temporary and will not persist.
  Whereas, if you were to define them in the config file or environment variables (as mentioned in link of your first comment) they will then persist.
  
  Additionally, if you add them in either environment variables, or the root flyway install directory as opposed to the project directory, the placeholders will be available for all instances of flyway.
  

  It worked when I tried. Thank you!
  
  Just a note to other devs, there are two "toml" format config files:
  - flyway.toml
  - flyway.user.toml
  
  I tried setting up my placeholders in either of them and it worked.
  
  NOTE: When you setup in flyway.user.toml you should specify full placehalder key name otherwise it will not be found.
  
  Example:
  Consider placeholder key "myKey", then in flyway.user.toml you should specify:
  flyway.placeholders.myKey = "myValue"
  
  In flyway.toml there are sections and you can spectify in "Global" flyway section, e.g.
  

  [flyway]
  mixed = true

  outOfOrder = true

  locations = [ "filesystem:migrations" ]

  validateMigrationNaming = true

  placeholders.myKey = "myValue"
  
  Notice, that "flyway" prefix was omitted, since its part of the [flyway] section that adds this namespace.
  
  For environment specific section you have to specify full placeholder name, for example H2Mem:
  

  [environments.H2Mem]

  url = "jdbc:h2:mem:testdb"

  user = "sa"

  flyway.placeholders.myKey = "myValue" <-- notice prefix "flyway."

  1 · Share on Twitter