The “Fill credentials from build” option is expected to pre-fill the credentials from the build but allow them to be overridden for the migration. However, the current behavior forces the use of the build credentials in all cases, even when the option is disabled or the credentials are manually overridden.
Observed Behavior:
1. Build credentials are always used during migration, even when:
• The “Fill credentials from build” option is not activated.
• Credentials are manually overridden.
2. This issue affects all existing deployments.
Workaround:
• The only way to bypass this issue is to use a just-in-time build.
Expected Behavior:
• The option should only pre-fill the credentials from the build without enforcing their usage during migration.
• Manually overridden credentials should take precedence if provided.
Where are you overriding the credentials? I am not seeing the same behavior you mention about overriding the credentials not working.
OttoDeploy is not dynamically filling the credentials every time you run a deployment, it grabs them from the build when you add files from a build to a deployment, unless the setting is turned off. Then the credentials are saved off to the OttoDeploy file. The “Fill credentials from build” option is only used when you add the files initially, are you seeing this on a new deployment when adding the files or just on deployments where you already had files added?
a) the migration has default credentials set for all files, no file-specific overrides. Source and target migration user is “migration”, pwd “migration” and passwords and key are secure on the target side. The migration then fails, the log shows that the command is trying to open the clone as user ‘root’, the user that was set for the build.
b) I add migration/migration and migration/*** as the override credentials to the file in question. The log also states the user ‘root’ for the clone file.
c) option on/off only affects the pre-filled override values but either with values deleted or set to “migration” the log displays the ‘root’ user.
The only way to work around this behavior is to run the build JIT.
I am guessing that most others are using the same credentials for the build and the migration. We build as ‘root’ to have access to the pre-build script and in the first migration we set all the production passwords and the encryption key. In DEV all accounts are root/root, user/user and so on. We also use individual root passwords in the solution files so we are utilizing a dedicated migration account which is the same for all files involved.
Ah ok I see it now. Its not an OttoDeploy problem, OttoFMS itself is pulling the credentials in from the build manifest if they are present. I’ll get a fix together for our next version, releasing sometime early January.