Skip to content

Commit b37f19b

Browse files
committed
Remove old samples
1 parent 9d493ce commit b37f19b

271 files changed

Lines changed: 1 addition & 27740 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

README.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,6 @@ This project provides the following:
88

99
* Pre-configured codespace with [K3s](https://k3s.io/) cluster via [K3d](https://k3d.io/)
1010
* MQTT Device Simulator
11-
* HTTP & GRPC Callout Server
1211

1312
> [!IMPORTANT]
1413
> Codespaces are easy to setup quickly and tear down later, but they're not suitable for performance evaluation or scale testing. For those scenarios, use a validated environment from the official documentation.

docs/ORGANIZATION.md

Lines changed: 1 addition & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -5,27 +5,17 @@
55
Explore IoT Operations is a collection of tools and samples for customers of Azure IoT Operations. To keep the project understandable and extensible to future additions, the following conventions should be followed for repository structure.
66

77
```
8-
├── lib/
9-
│ ├── library1/
10-
│ ├── ...
11-
│ ├── libraryN/
128
├── samples/
139
│ ├── sample1/
1410
│ ├── ...
1511
│ ├── sampleN/
16-
├── scripts/
1712
├── tutorials/
1813
└── README.md
1914
```
2015

21-
**Libraries** (`./lib`) are shared between multiple tools or samples.
22-
2316
**Samples** (`./samples`) are tools or code samples which can be written in any language. They should be given a descriptive name which adequately describes their purpose, and should include some level of documentation regarding their usage.
24-
25-
**Scripts** (`./scripts`) are bash scripts smaller than a tool or sample which are in some way used for setup.
26-
2717
**Tutorials** (`./tutorials`) are collections of code and documentation which are used together to provide a step-by-step walkthrough to demonstrate the capabilities of some feature of Azure IoT Operations. These typically serve a more narrow scope than that of a tool or code sample, designed to exercise specific facets of Azure IoT Operations.
2818

2919
## Linting, Formatting, and Testing Requirements
3020

31-
Linting, formatting, and testing are not required but are highly recommended. The mage library under `./lib/mage` is provided for golang projects and offers some basic commands for linting, formatting, building, testing, and assuring test coverage bars. Comments describe each function within the library. See `./samples/industrial-data-simulator/mage.go` for an example of how this library is used.
21+
Linting, formatting, and testing are not required but are highly recommended.

lib/env/env.go

Lines changed: 0 additions & 98 deletions
This file was deleted.

lib/env/env_test.go

Lines changed: 0 additions & 166 deletions
This file was deleted.

lib/env/errors.go

Lines changed: 0 additions & 25 deletions
This file was deleted.

lib/env/go.mod

Lines changed: 0 additions & 13 deletions
This file was deleted.

lib/env/go.sum

Lines changed: 0 additions & 10 deletions
This file was deleted.

lib/logger/go.mod

Lines changed: 0 additions & 11 deletions
This file was deleted.

lib/logger/go.sum

Lines changed: 0 additions & 15 deletions
This file was deleted.

0 commit comments

Comments
 (0)