Skip to content
This repository has been archived by the owner on Dec 5, 2024. It is now read-only.

Rename references to concerto #85

Open
pcantera opened this issue Feb 8, 2022 · 0 comments
Open

Rename references to concerto #85

pcantera opened this issue Feb 8, 2022 · 0 comments
Assignees
Labels

Comments

@pcantera
Copy link
Contributor

pcantera commented Feb 8, 2022

Along the project, the 'concerto' word is being used in order to name configuration files, environment variables, used in API headers, ... due a legacy context and be continued with pre-existing style..

Now it's time, as a need, to apply required changes in those contexts - coordinating with IMCO team-; focused on those which affect to integration layers or customer use case.

  • FILES:
    brownfield/register.go
    polling/register.go
    README.md
    main.go
    config.go
    webservice.go
    linux_settings.go

  • CONFIG FILE
    .concerto
    xml <concerto ...>
    log

  • ENVIRONMENT VARIABLES
    CONCERTO_CA_CERT
    CONCERTO_CLIENT_CERT
    CONCERTO_CLIENT_KEY
    CONCERTO_CONFIG
    CONCERTO_ENDPOINT
    CONCERTO_URL
    CONCERTO_BROWNFIELD_TOKEN
    CONCERTO_COMMAND_POLLING_TOKEN
    CONCERTO_SERVER_ID
    CONCERTO_FORMATTER

  • Post
    X-Concerto-Brownfield-Token

  • concerto-setup
    Tmp file

NOTE: This is not an issue focused on general review for this word -there's another issue and branch focused on this and a general deep review of the project on the way- , but for integration point of view, such as the detected ones.

Expected Behavior

Current Behavior

Possible Solution

Steps to Reproduce (for bugs)

1.
2.
3.
4.

Context and environment

@pcantera pcantera self-assigned this Feb 8, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant