[
https://issues.jboss.org/browse/JBIDE-21710?page=com.atlassian.jira.plugi...
]
Navid Shaikh commented on JBIDE-21710:
--------------------------------------
The problem is that adbinfo and service-manager return different cert
paths:
That's a fix, earlier we were having multiple hidden directories with dot (.)
[.vagrant and .docker]. See
<
https://github.com/projectatomic/vagrant-service-manager/issues/4> for more
information.
vagrant-service-manager plugin creates the `docker` directory in secrets_path of vagrant
and copies the certs over. The path is correct and certs are copied over in that
directory.
[CDK] replace calls to adbinfo plugin with service-manager plugin
-----------------------------------------------------------------
Key: JBIDE-21710
URL:
https://issues.jboss.org/browse/JBIDE-21710
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: cdk, server
Reporter: Navid Shaikh
Assignee: Rob Stryker
Priority: Blocker
Fix For: 4.3.1.CR1
vagrant-service-manager plugin [1] is a successor for vagrant-adbinfo plugin [2].
All further development towards displaying and configuring provider [docker, openshift,
kubernetes, etc] information from ADB / CDK, will happen in vagrant-service-manager
plugin.
Equivalent functionality from vagrant-adbinfo plugin is now ported to
vagrant-service-manager plugin.
To display docker connection information from vagrant box,
using adbinfo
```
$ vagrant adbinfo
```
using service-manager
```
$vagrant service-manager env docker
```
Kindly update the tooling which are using adbinfo plugin with service-manager command.
Note: adbinfo plugin has a dependency on `scp` / `pscp` utility for copying certs.
service-manager plugin does not need `scp` / `pscp` utility to copy the certs.
[1]
https://github.com/projectatomic/vagrant-service-manager
[2]
https://github.com/projectatomic/vagrant-adbinfo
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)