Closed joakibj closed 4 years ago
The Jboss/WAS app-config.xml offers the possibility to expose a fasit endpoint resource to all zones through the <exportToZone> element.
app-config.xml
<exportToZone>
<exposedSoap name="InnsynJournal_v2" path="/services/innsynjournal/v2" wsdlGroupId="no.nav.tjenester" wsdlArtifactId="nav-innsynJournal-v2-tjenestespesifikasjon" wsdlVersion="2.0.2" securityToken="SAML"> <exportToZone>SBS</exportToZone> </exposedSoap>
Currently naisd only offers the ability to expose a fasit resource to the same zone the app is deployed to.
We suggest an equivalent in the nais.yaml spec to accomodate the same behaviour for migration purposes.
nais.yaml
Something like a zone, exposeToZone or similar attribute:
zone
exposeToZone
- alias: InnsynJournal_v2 resourceType: webserviceendpoint path: /services/innsynjournal/v2 wsdlGroupId: no.nav.tjenester wsdlArtifactId: nav-innsynJournal-v2-tjenestespesifikasjon wsdlVersion: 2.0.2 securityToken: SAML zone: all
This way other apps in different zones than e.g. fss can retrieve this resource from fasit.
fss
The Jboss/WAS
app-config.xml
offers the possibility to expose a fasit endpoint resource to all zones through the<exportToZone>
element.Currently naisd only offers the ability to expose a fasit resource to the same zone the app is deployed to.
We suggest an equivalent in the
nais.yaml
spec to accomodate the same behaviour for migration purposes.Something like a
zone
,exposeToZone
or similar attribute:This way other apps in different zones than e.g.
fss
can retrieve this resource from fasit.