Service gets duplicated in the portal on client restart

[njt1982]

I asked this on twitter first... https://twitter.com/nick_thompson/status/990662680842330113

Initially, I thought this was caused by some kind of change in fingerprint of the software versions (like when nginx upgrades):

But then I just restarted the client (service amplify-agent restart) and another one came up in the list.

Should I write the UUID to the config?

It looks like, back in December, the app was changed to not write the UUID to the config. https://github.com/nginxinc/nginx-amplify-agent/commit/4299c79eab210e5201f4776fdeccb9364f9538fc

[gshulegaard]

For some managed environments, modifying the config file is undesirable. We did however add a new config value that you can use to enable writing the UUID automatically to the config:

[credentials]
store_uuid=True  # with this set to true the agent will write UUID to the config like before

With this flag set to True the original agent behavior will be restored.

[Danrancan]

For some managed environments, modifying the config file is undesirable. We did however add a new config value that you can use to enable writing the UUID automatically to the config:

[credentials]
store_uuid=True  # with this set to true the agent will write UUID to the config like before

With this flag set to True the original agent behavior will be restored.

I'm having the same problem. Where exactly should we put those lines? What file?

[richbrowne]

@nkashiv Could you have a look?

[nkashiv]

I'm having the same problem. Where exactly should we put those lines? What file?

@Danrancan You can add it to the Amplify Agent's config file /etc/amplify-agent/agent.conf under the [credentials] section.