Skip to content

Unable to use clients repository proxy for the 'hardcoded' specs path #239

@Robin-Bezuijen

Description

@Robin-Bezuijen

When using a client repo proxy (which is normal on customer projects not sharing the master credentials) the wagon urls will not work:

                    <configuration>
                        <url>https://repo.backbase.com/specs/accessgroup-integration-service</url>
                        <fromFile>accessgroup-integration-inbound-api-v2.2.0.yaml</fromFile>
                    </configuration>

the /specs path is not a repository (under /repo/specs)

Possible fixes:

  1. Add the specs to the repo to make https://repo.backbase.com/repo/specs/accessgroup-integration-service/accessgroup-integration-inbound-api-v2.2.0.yaml work.

  2. Use the bom and uzip all specs from a bom version to the downloaded-api folder:

                             <artifactItem>
                                 <groupId>com.backbase.dbs</groupId>
                                 <artifactId>banking-services-bom</artifactId>
                                 <version>${dbs-bom.version}</version>
                                 <classifier>api</classifier>
                                 <type>zip</type>
                                 <outputDirectory>${project.build.directory}/specs</outputDirectory>
                             </artifactItem>
    

Option 2 makes way more sense because then fuel is in sync with a BB release.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions