Change repository configuration of a scoped App

[Sashi K1]

Hi

Is that possible to change repository configuration once we map a Scoped Application to a repository? In my case, we have App published to repository. Now wanted to change repository configuration instead of cloning repository to another repository. How could I do that?

I tried 'sys_repo_config.list' and tried edit config mappings. I see runtime exceptions saying registered repository and given repository URL is not same. Couldn't find where is that 'registered' config information stored.

1. Could we change current repository of a scoped app without publishing app to an update set, z-boot instance and reload with new configuration information.

Any help greatly appreciated!

[Chuck Tomasi · Accepted solution]

Hi Sahikanth,

There is currently no way to point to a new repo on the instance. There are two alternatives.

First, you can use the clone repo as you noted. Once cloned, you need to remove the original app and import the app from the new repo.

The second is similar only you export your app to an update set, delete it, create the new repo, import the update set and reconnect to the new repo.

As you can see, both involve deleting the app on the instance.

[Sashi K1]

Thank you, that make sense. I was checking is there anyway other than two above to change pointers. Looks like system has a secret way to keep configuration information other than sys_repo_config table, may be in a metadata.

Anyway, thanks for confirming current possibilities. Appreciate your quick help!

[john_duchock]

Cannot deploy to two gits?  that is a serious limitation 😞

[David Hadwin2]

Hi John,

This is old...but how is this limiting you?

If you wanted to keep two repos the same, you could push to one repo (the main one) fork it and have it mirrored to the forked repo. This would achieve the same thing as "deploy[ing] to two gits" unless you mean deploying to both GitLab AND GitHub...then, you'd be right...but I'd have no idea why you'd want to do that anyways.