![]() The Elastic Beanstalk configuration does tag the database, using a Name tag specified in the Elastic Beanstalk configuration, so the answer seemed obvious: Use the tag information to identify the database. This meant that there was the potential for the database in question to be removed from RDS and a new one set up, which meant a new unique identifier for the database I wanted to create manual database snapshots from. ![]() However in this case, the database was being created as part of an Elastic Beanstalk configuration. Normally this is a straightforward process because you can use the database’s unique identifier when requesting the database snapshot to be created. Recently, I was working on a task where I wanted to set up an automated process to create manual database snapshots for a database hosted in Amazon’s RDS service. For more details, please see below the jump. The answer was in how the package’s package identifier was set up. SapMachine Java 17 LTS installed, then SapMachine Java 11 LTS is installed.SapMachine Java 11 LTS installed, then SapMachine Java 17 LTS is installed.But what was causing this behavior? Also, why was it happening in this order? After a re-review of the script and additional testing, I was able to rule out the script as the problem. It is supposed to remove an existing SapMachine Java 17 LTS installation with the same version info, but it should not have also been removing SapMachine Java 11 LTS. I double-checked the preinstall script for the SapMachine Java 17 LTS installer. SapMachine Java 11 LTS installed, then SapMachine Java 17 LTS is installed – SapMachine Java 11 LTS is removed, only SapMachine Java 17 LTS is installed now.SapMachine Java 17 LTS installed, then SapMachine Java 11 LTS is installed – no problem.SapMachine Java 17 LTS is installed by itself – no problem.When I ran the SapMachine Java 17 LTS installer that was being generated by AutoPkg, I was seeing the following behavior: As part of developing new AutoPkg recipes to support SapMachine‘s new Long Term Support (LTS) distribution for Java 17, I ran into a curious problem when testing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |