Make dev and staging libraries default to upstream | Adobe Higher Education
Skip to main content
Jennifer_Kunz
Adobe Champion
Jennifer_KunzAdobe Champion
Adobe Champion
March 6, 2019
Accepted

Make dev and staging libraries default to upstream

  • March 6, 2019
  • 4 Antworten
  • 10077 Ansichten

Currently, if there is no library assigned to a dev or staging environment, it 404s. This can (reasonably) bother developers and break analytics testing on dev/staging/QA servers.

Ideally, if an environment does NOT have a library currently on it, it would just use whatever is currently upstream in prod.

    4 Antworten

    L
    lulufrancis
    March 6, 2019

    Adding an option to allow enable/disable upstream would be helpful as well.

    thebenrobb
    Adobe Employee
    thebenrobbAdobe Employee
    Adobe Employee
    April 16, 2019

    We had some Akamai problems in the past that led to Dev Libraries being removed when they shouldn't be, but that has been fixed now.  The only time an Environment should ever return a 404 now is when it is first created and has never been built in.  And defaulting to Prod often wouldn't help in that scenario because it wouldn't have anything in it either.

    One idea that has been floated is that when an Environment is created, we just drop an empty build there so that it wouldn't 404.  Curious to hear people's thoughts.

    Jennifer_Kunz
    Adobe Champion
    Jennifer_KunzAdobe ChampionAutor
    Adobe Champion
    April 16, 2019

    I think that'd be great, as a bare minimum.

    thebenrobb
    Adobe Employee
    thebenrobbAdobe Employee
    Adobe Employee
    February 18, 2020

    Building empty libraries for new environments is on the roadmap for this year.

    Allgemeine NutzungsbedingungenAccessibility statement

    Loading footer...