bug: Not automatically updating app source?

[HWiese1980]

Describe the bug

v2.2.21-1

I have a deployment from a GitLab repo. The metadata is updated upon pushing, but the deployed source has an old state, is only updated when I go to "Update App Source" and manually update it. I would expect the app source to be updated automatically, especially when the allegedly deployed commit is the newest on the corresponding branch.

Credentials are correct, otherwise I probably would not see the newest commit in the metadata.

Cheers

Are you working on this issue?

No

[tanmoysrt]

@HWiese1980
Are you expecting to sync the docker configuration from your project ?

[HWiese1980]

Well, I'm expecting to sync the whole source from my gitlab repo, as does when I use Update App Source, only automatically upon push/deploy, to have the exact repo status deployed that the commit points to, as shown in the Swiftwave app details view.

[tanmoysrt]

Got it. That's expected.

Only thing that doesn't get picked, while deploying is Dockerfile. Else, people can't modify Dockerfile on swiftwave.
I thought it's fine, because Dockerfile in a project isn't going to change with each update.

---

Anyway we can provide some option to set some config to pick latest Dockerfile from project only.

Will add that in V3.
For now, I am not doing much changes on V2 (kind of frozen now).

[HWiese1980]

Yeah, okay.

It's not just the Dockerfile. The Dockerfile itself does not really change much indeed, after it has been kind of consolidated. But the rest of the project does of course change to some extent with every commit. I need to reliably deploy updated sources after I committed and pushed my changes, even if the Dockerfile itself may remain as it is. The commit hash/commit message as shown in the deployment should be in sync with what is actually running on the target after its deployment.