File Overrides autofilled for source!

OttoDeploy
1

When adding new files to a Sub-Deployment the source credentials are automatically added to the files creating instant file overrides.

Almost cried because I have searched for the reason fo the failed deployment for 2 hours. Then saw that file overrides were active on newly added files and i had a missmatch in the initial setting. Corrected it in File Options but still failed. Then saw the overrides. Interestingly only the source creds are filled, destination stays empty.

2

Hey Tobias,

Are you using a build as your source? The credentials that you enter for your build get auto-filled into deployments when you use a build as your source.

-Kyle

3

Ahh. thanks. Can we NOT do that? It would be better to have them autofilled in the subdeployment when we use a build, not the files themselves.
Many thanks
Tobias

4

Hey Tobias,

If OttoDeploy filled it on the default options, which file would it choose the credentials from to fill in? The first one? What if they have different credentials?

In the current state, the files all have their own credentials filled in, and there is a UI different when they have overrides filled in so you can tell that something has been added.

I could see adding a setting for turning off the filling in of the credentials from the credentials in the build, is that something you would like?

-Kyle

5

Since I did not add any file overrides when creating the build why should it be added as overrides when I add files from the build to a sub deployment? Since I can only choose files from that specific build.

If I added overrides in the build itself I would expect them - and only them - to show up when adding the files.

But if that is too difficult I would prefer to have a switch to turn off adding credentials to a build.

Many thanks!

6

Hey Tobias,

I get that. The way builds work does not actually store the overrides vs. defaults in the build on your server. The overrides/defaults concept is just an ease of use feature for OttoDeploy. Later, when OttoDeploy pulls the build in, it is pulling the build from your server and can only get the creds on each individual file, not whatever defaults you may have set.

I’ll add a setting to turn off adding the creds by default to our list.

-Kyle

7

:heart: Thanks a lot! Looking forward to it!

1 Like